home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Graphics Plus
/
Graphics Plus.iso
/
msdos
/
viewers
/
shwpcx10
/
showpcx.doc
next >
Wrap
Text File
|
1991-12-29
|
7KB
|
162 lines
S H O W P C X 1.0
==================
Free Software by TapirSoft Gisbert W.Selke
Dec 1991
ShowPCX is a simple programme that displays PCX graphics. Support for
EGA, VGA, and Hercules adapters is built in; others may be used in
conjunction with the appropriate BGI driver from Borland. As a bonus,
support for the Tseng ET4000 chip is also built in; with this driver,
you can enjoy the greater resolution this chip offers. (Cf. below for
details.)
ShowPCX is not fancy; I just needed a simple PCX viewer that was command
line driven and was completely royalty free -- that was the incentive
behind writing this programme.
Usage is straightforward: just call ShowPCX from the DOS prompt, naming
the PCX files you want to view on the command line. Example:
showpcx test1 test2 test3
(The file extension .PCX is assumed, unless you include a period in the
file name, e.g., test1.pcc.) ShowPCX will display each image, wait for
you to press a key, and then proceed to the next image, if any is left;
after the last image, ShowPCX will return you to the DOS prompt. Any
ordinary key (except, of course, SHIFT, CTRL, etc) will do; however,
typing ESC, Q or CTRL-C will immediately return you to the DOS prompt,
skipping any image that may be left. If the image is too large to fit on
the screen, you will just see the top left corner -- there is no way of
walking around using the cursor keys or a rodent. (Cf. the '/s' option
below, though.)
Assuming that there are no other PCX files in the current directory that
start with test..., you could achieve the same result as above by typing
showpcx test?
or
showpcx test*
I.e., the usual DOS wildcard characters may be used. (The order in which
the files are shown may differ -- ShowPCX uses the same order as the DOS
command 'dir'.) Of course, path names can be used where necessary.
A problem occurs whenever you have to name more files than will fit on
the DOS command line, which is restricted by DOS to 128 characters. If
you cannot make clever use of wildcards, then you can build a plain text
file that contains the names of the PCX files, one or more per line.
Then pass the name of this text file to ShowPCX, preceding it with the @
character. Example: suppose your text file is named SLIDE.LST and
contains the following lines:
test1
test2
test3
Then calling
showpcx @slide.lst
will yield the same result as the examples above. (Note that there is no
implied file extension in this case.) Both forms of naming files can be
mixed freely, but you cannot nest file lists, that is, you can use '@'
notation on the command line only.
There's one potential catch here: what do you do if your PCX file is
called @TEST.PCX, e.g.? Calling 'showpcx @test' would result in ShowPCX
looking for a list file called 'TEST', which is not what you'd want. The
work-around in this case is to specify 'showpcx .\@test', which refers
to the file '@TEST.PCX' in the current directory.
There are a few options that slightly change the behaviour of ShowPCX;
they are listed below:
/c : centre image
/cx : centre image horizontally only
/cy : centre image vertically only
/d<num> : delay in milliseconds after each image (slide show)
/e<num> : extended VGA mode (use at your own risk!)
/h : display help
/m : force monochrome mode
/p : use alternate packing strategy for scaling
/q : quiet behaviour (don't beep)
/s[<num>] : scale image by factor 1/<num> (0 = autoscale)
/sx[<num>] : scale horizontally only
/sy[<num>] : scale vertically only
/v : verbose image info
/z : zebra monochrome mode
Example: if you want to run the above example as a slide show with
automatic screen changes every 10 seconds, call
showpcx test* /d10000
While displaying, you can always shorten the delay by pressing any key.
We can further complicate this example by making sure that images are
nicely centred and scaled (proportionally) to fit the screen:
showpcx test* /d10000 /c /s
If, in addition, you have a Tseng ET4000-based SuperVGA, which supports
a resolution of 1024*768 at 256 colours, you may want to call
showpcx test* /d10000 /c /s /e4
The switches can be specified anywhere on the command line, but they
cannot be concatenated. I.e., '/cm' is not valid, and neither is '/c/m'
-- use '/c /m' instead. Note that '/c' is the same as '/cx /cy', but
'/s' is, in general, not the same as '/sx /sy'! The numbers must be
integer, by the way.
The result of the switches should mostly be clear from the above;
otherwise, just try them out -- that's easier than to have it explained.
A few hints, though: it is hard to tell beforehand whether the '/p' and
'/z' switches should be used; if you use packing and/or monochrome
mode, and the default behaviour is unsatisfactory, try these switches.
The '/e' switch is somewhat dangerous -- if you know enough about your
graphics adapter and the BGI driver you probably have supplied yourself,
you can force the video mode to whatever is possible, even if ShowPCX
has no built-in knowlege about it. If used improperly, this may damage
your video adapter and/or screen -- caveat emptor! The built-in
driver for the ET4000 supports the modes:
/e0 : 320x200x256 Standard VGA
/e1 : 640x400x256 SuperVGA
/e2 : 640x480x256 SuperVGA
/e3 : 800x600x256 SuperVGA
/e4 : 1024x768x256 SuperVGA
Legal stuff:
This is free software; as such, it comes without any warranties
whatsoever. It works for me; I cannot be held responsible for any
damage caused. You have been warned. If it doesn't work for you, make it
fit for yourself -- that's why the source is included. Just give credit
where credit is due. Otherwise, this software can be used and copied
freely; however, it must not be sold for profit.
The name BGI is owned by Borland International; the name ET4000 is
property of Tseng Labs. The format of PCX files and the name of this
format were created by ZSoft. The SVGA256.BGI driver for the ET4000 chip
was supplied by Jordan P. Hargrave and is highly recommended. Please
consider ordering and registering his unit.
If anything goes wrong (and it sure will...), I can, for the time being,
be contacted at one of these addresses:
TapirSoft <s00100@dbnrhrz1.bitnet>
Gisbert W.Selke <s00100@ibm.rhrz1.uni-bonn.de>
Ermekeilstraße 28 <gisbert@watsun.cc.columbia.edu>
D-5300 Bonn 1
Germany
Enjoy!